General: Restore and deprecate wp_register_development_scripts#10702
General: Restore and deprecate wp_register_development_scripts#10702youknowriad wants to merge 2 commits intoWordPress:trunkfrom
wp_register_development_scripts#10702Conversation
The function was removed in [59620] but should be deprecated instead of removed outright to maintain backward compatibility. Props youknowriad. See #62648. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
Co-authored-by: Weston Ruter <westonruter@gmail.com>
2 participants
Summary
wp_register_development_scriptsfunction that was removed in commit 22294afWP_DEBUGis enabledBackground
WordPress Core policy is to deprecate functions rather than remove them outright to maintain backward compatibility. This PR restores the function signature while deprecating it properly.
Test plan
wp_register_development_scripts()no longer causes a fatal errorWP_DEBUGenabled, calling the function triggers a deprecation notice🤖 Generated with Claude Code